Why extra option instead of having option in root level in query?

The query itself must either be object or string and it's nice to have options as a function. It's also the least intrusive change.

Maybe we should name it as plugins?

Yea we could do query.plugins instead of query.options; that works. 👍

Thanks! Let me know when a new version is published @ai 😄

I just need to update docs, add result.messages with dependencies and we are ready for release.

👌

I finished all changes and ready for release. Could you test this plugin on real application? (Just replace version in package.json to postcss/postcss-loader)

webpack v2.1.0-beta.25

LoaderOptionsPlugin: ✅
postcss.config.js: 🚫

I'm on it... :)

Will try and get this working will my configuration tonight 😄

@ai Running into a few hiccups. First of which is ./node_modules/postcss-load-config/index.js. There's some mismatch between versions going on here, where that file is trying to require postcss-load-options/lib/loadOptions.js which doesn't exist; the file is instead called postcss-load-options/lib/options.js. I'm not sure which version is intended to be correct or where the mismatch is coming from.

@ai The way you've refactored parseOptions also results in failing to pass the webpack context through.

return parseOptions(options, pack);

should be:

return parseOptions(loader, options, pack);

and then:

function parseOptions(context, options, pack) {
// ...
options = options.call(context, context);

This will break postcss-imports (and possibly more) otherwise.

You can verify these by checking out the branch here: webpack-config/webpack-config-postcss#10 and running npm run smoke.

@izaakschroeder postcss-load-config issue should be fixed now.

Thanks @michael-ciniawsky it is 😄 Just waiting on @ai now.